test: unittest for stakingmiddleware module #426
Conversation
tungleanh0902
changed the title
tungleanh0902
force-pushed
the
test/stakingmiddleware
branch
2 times, most recently
from
2d469e2 to
2d035eb
Compare
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
tungleanh0902
force-pushed
the
test/stakingmiddleware
branch
from
c080fdd to
6e81d28
Compare
tungleanh0902
force-pushed
the
test/stakingmiddleware
branch
from
6e81d28 to
be970fc
Compare
|
interchain tests dont pass |
why not? Can you fix? |
|
can you guys check access token settings? the PR here is forbidden from pulling required image in Interchain Tests 
|
checking |
When you fork a repository in GitHub, the forked repository inherits certain permissions and settings from the original repository, including access controls for Docker images in GHCR. By default, forked repositories do not have permissions to push Docker images to GHCR, even if you have write access to the forked repository. Checking the members of the repo I saw that you have write access to it, you can generate a Personal Access Token (PAT) with the necessary permissions (read:packages and write:packages) and use it in your GitHub Actions workflow to authenticate and push Docker images to GHCR. Let me know if that works please. |
|
Hi @Ciejo, I added my PAT with r/w packages into repository secrets of the forked repo but it stays the same error. Does your repo have repo secret named GITHUB_TOKEN? Github does not allow me to add a secret named GITHUB_ so I have to change its name. (notional-labs#12) |
Hello, sorry for the delay. I already added a PAT to our company organization. Can you merge your PR in notional repo and try to run again the workflow please? |
No description provided.